ty for making this PR

Greep while we're waiting for this PR to be merged in I will be using the fork you made!

Thanks for this guys. I'll be moving to this as well for now. hopefully this gets merged in soon.

Looks like I have one approval but need 2 more approvals

We have some approvals but this is the blocker:
"First-time contributors need a maintainer to approve running workflows. Learn more.
1 successful check"

Who is a maintainer?

Maybe
TimeForANinja
VoltrexMaster
fent

Can help as maintainers?

It seems the project needs more maintainers or at least in different time zones as this critical issue has made the library unusable for a day. Anyway impressive effort solving it, thanks so much!

It's been nearly an additional twelve hours. This is a breaking change and needs to be fixed ASAP.

It's been nearly an additional twelve hours. This is a breaking change and needs to be fixed ASAP.

This is an open source project that is being provided to you for free. No one asked you to use it, no one sold it to you, and most importantly, no one owes you anything. The license is clear on this: 'THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED...'

If you really need this "fixed ASAP", you can do it yourself. The code is right there in this pull request. Here's one of many ways to hot-patch an existing installation.

cd node_modules/ytdl-core
curl -L https://github.com/fent/node-ytdl-core/pull/1111.patch | patch lib/sig.js

You could also follow the suggestion at #1110 (comment) to use the patch author's fork.

Or you could downgrade to 4.10.0.

@dskaiser82 @GreepTheSheep This repository uses semantic-release so you'll probably need to edit the first line of the commit message to trigger a release. Maybe use git commit --amend to change it to fix: adjust for YouTube's new signature and then force push to the PR branch?

@Trott Agree with you btw on the open source comment, and the multiple temp solutions out there.
I'll update the commit, but I dont think thats the blocker now.

It's "2 workflows awaiting approval
First-time contributors need a maintainer to approve running workflows. Learn more.
1 successful check"

I dont think we have any maintainers paying attention to the PR.....even so yes I can ammend the commit

I'll update the commit, but I dont think thats the blocker now.

Yeah, I don't think it's a blocker at the moment. I'm just saying that you might want to have the commit message formatted the way the tool will expect it so that it doesn't end up delaying things later on.

I dont think we have any maintainers paying attention to the PR

@fent @TimeForANinja

"A repository owned by a personal account has two permission levels: the repository owner and collaborators. For more information, see "Permission levels for a personal account repository."

Need that "write access".

@Trott When the Merge button shows, we will do a squashed commit the GitHub GUI let's the user do. We can squash then.
We have the same flow at work.

This is an example of a squashed commit:

feat: add IPv6 block rotating (#713)

* IPv6 Rotating ^-^

* linter got mad at missing semicolon nice

* Fixing format

Fixing the format of files so eslint does not throw any errors.

* adding colon

* added test for IPv6 Block

btw using close keyword in pr description like "close #issueid" will make a link to the original issue and automatically close the issue when the pr was merged, it might be better if so

Ty for being so fast with this fix 🚀

@TimeForANinja Anything else that needs to happen here before this can be merged?

@Trott I don't think so. I used it with my app and it works very well.

@Trott I don't think so. I used it with my app and it works very well.

Thanks, but I was addressing @TimeForANinja specifically because they are (AFAICT) the one person who has been active in this pull request who has the permission to merge the commit. It was a hopefully-polite way of saying "bump, please--can we merge this now?"

@TimeForANinja Anything else that needs to happen here before this can be merged?

just one thing @Trott and @dskaiser82
if it's possible to get this resolved by doing some minor, quick updates to the cutAfterJSON method i'd prefer it

tried some stuff
you can find my changes here and the branch itself here
it worked for the hand full of requests i did - feel free to comment on it

no idea what exactly went wrong here #1110 (comment)
did test for try { xxx } catches (e) { xxx } in the text and they got recognized fine

@TimeForANinja

I did this PR from @GreepTheSheep 's Fork. I've personally been using the fork and know this code update works. With that being said, we can go with your changes instead and I can close this PR.

As you are a maintainer just advise what you'd like to do.

cc: @Trott

@TimeForANinja

you can find my changes here and the branch itself here
it worked for the hand full of requests i did - feel free to comment on it

One of the array elements found in a base.js n-code extraction today is

    ... -1816574795, '",;/[;', function ...

which would break cutAfterJSON because you would have an orphan double quote. Perhaps if single quotes and back quotes are also added as string markers, that would do it.

I also prefer to keep cutAfterJSON to extract the complete js function. Using

    .join("");}

as the end marker (in the proposed solution) will break as soon as Youtube change it to something else. Whereas a robust cutAfterJSON would assimilate any future changes.

I vouch for @gatecrasher777 change. At least the fork and this PR.

@fent Any chance you can add one more Maintainer to me, @Trott , @gatecrasher777 or @GreepTheSheep ?

We have a fix...we have a PR that at the most is long term and at least a good band aid to fix for all the users that use this.

Maybe it's time to give up on this main Repo? This process is sad and disheartending.....I get if current maintainets are over or it....I do...But can at leat communicate this and the need to jump to new fork or repo?

cc:
@TimeForANinja

And I get it..... @fent makes some thing awesome that devs use... Coders like @TimeForANinja help maintain it. Countless hours are put in to make it better and keep it a live....Noone is getting paid.....over time energy and momentum is lost....

But for the devs that do give a shit about and want to help....puts us in an frustrating situation.....which we have options....
Anyways I get it....

replaced by #1126
still ty for the pr and finding the problem

Ironically enough, this pr actually fixes the current regex issue (#1131), unlike #1126, which is already throwing errors again.